Event Management System for Facilitating User Interactions at a Venue

ABSTRACT

A user computing device is loaded with a ticket identifier for an event and configured to act as a beacon device transmitting a unique identifier. At the event, a first event computing device located at a first area of the venue (e.g., the main entrance) detects the transmitted beacon and interacts with the user computing device to authenticate the ticket and enable access to the first area. A second event computing device located at a second area of the venue (e.g., VIP area) detects the transmitted beacon and interacts with the user computing device to authenticate the ticket and enable access to the second area.

CROSS-REFERENCE

This application is a continuation of U.S. application Ser. No.16/829,382 entitled Event Management System for Facilitating UserInteractions at a Venue, filed Aug. 18, 2015, and incorporated herein byreference in its entirety.

TECHNICAL FIELD

This disclosure relates generally to a network-based event managementsystem, and in particular, to the use of beacons at an event to initiateprocess flows that facilitate the user experience while the user isattending the event.

BACKGROUND

Websites are commonly configured to allow user devices to conduct a widevariety of actions online, such as viewing content, writing reviews,ordering items, purchasing tickets, etc. The website presents the userdevice with a menu of action choices, and upon user selection, thewebsite typically redirects the user device to a different webpage wherethe action is completed.

For example, some websites allow users to organize and administer eventsusing an online event management system, such as the Eventbrite eventmanagement platform hosted by Eventbrite, Inc., of San Francisco, Calif.(see www.eventbrite.com). An event organizer may use such a system toorganize and manage various aspects of an event, such as attendeeregistrations, ticket sales, event promotion, attendee check-in at theevent, etc. An online event management system may also allow customersto view event profiles, register for events, purchase tickets forevents, check-in for events, etc.

An event management system may also be utilized to manage event-relatedtasks conducted at the venue of a scheduled event, such as sales ofmerchandise, refreshments and other items, event registration and/orticketing, check-in of registered event attendees, communication withevent attendees, etc. However, many problems currently exist in how anevent management system is utilized to manage event-related tasks at anevent. As an example, customer purchases using credit cards and cash atdedicated point of sale terminals can result in long and slow movinglines. As a further example, checking in to an event using a bar codescanner to scan a physical ticket can result in a slow entry process. Asyet another example, the use of a near-field communication (NFC) systemwould provide a faster check in process and an improved purchaseexperience at an event, but NFC communications require close proximityand specialized equipment that may not be available to a large amount ofevent attendees. As a further example, the use of a radio-frequencyidentification (RFID) system may also provide a faster check in processand an improved purchase experience at the event, but an RFID systemrequires the shipping and fulfillment of specialized bracelets to eventattendees prior to an event.

Thus, it would be desirable to continue to expand the number of featuresthat can be provided by the event management system at the event tofurther enhance the experience of both event attendees and eventorganizers. Further, such enhancement could provide a faster check inprocedure at the event, quick and easy purchases at the event, anddelivery of relevant information and more flexibility as to where andhow these experiences are delivered to event attendees.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an event management system.

FIG. 2 is an illustration of a check-in system at an event.

FIG. 3 is a schematic diagram of a system configuration for an eventillustrating the deployment of beacons and check-in devices at an event.

FIG. 4 is a flow diagram illustrating a process for detecting and actingon a unique identifier generated by a beacon device and detected by auser device.

FIG. 5 is a flow diagram illustrating a process for checking a user intoan event with a user device.

FIG. 6 is a flow diagram illustrating a process for granting access to auser for a restricted area at an event.

FIG. 7A is a flow diagram illustrating a process for detecting andacting on a unique identifier generated as a beacon by a user device.

FIG. 7B is a flow diagram illustrating an alternative process fordetecting and acting on a unique identifier generated as a beacon by auser device.

FIG. 8 is a block diagram illustrating one embodiment of a computingsystem implemented as an event management system.

DETAILED DESCRIPTION 1. Overview

An event management system is disclosed that utilizes one or more beacongenerating devices at an event in order to initiate process flows forspecific event-related tasks. Each beacon generating device isconfigured to periodically and repeatedly transmit the same information,namely, a unique identifier (“UID”) that is associated with the specificbeacon generating device.

In one embodiment, a user's mobile communications device can beconfigured to listen for specific UIDs and other transmissions beingbroadcast by a beacon generating device. Upon detecting a UID from abeacon generating device that is transmitting its UID at an event, theuser device sends the detected UID to the event management server. Theserver looks up the UID and returns a specific event-related processflow associated with the UID to the user device and/or the beacon deviceand/or an event organizer device located at the event. As an example, aprocess flow may be delivered to the user device to enable the user tocheck in to the event or to complete a purchase at the event or toreceive information or communications related to the event.

In another embodiment, the user's mobile communications device can alsobe configured to broadcast its own UID, i.e., to act as a beacongenerating device. When the beacon of the user device is within range ofa beacon device or any other adequately configured computer device atthe event, the event management system can perform a number of contextspecific actions. As an example, upon the user approaching a gate at theevent, the event management system could detect and recognize thebroadcast UID of the user device as being registered or ticketed for theevent, and run a process to check in the user as being in attendance atthe event, or further, to run a process to admit the user to the eventif he has a valid ticket or registration. As a further example, uponapproaching the event, or a point of sale location at the event, theevent management system could run a process to perform a purchasetransaction for a ticket to the event or for other goods and services,with the user's purchase credentials stored on the event managementsystem and linked to the specific UID that is being transmitted by theuser device.

2. System Architecture

FIG. 1 illustrates an embodiment of an event management system 10.System 10 includes a first user 1 having a client system 11, a seconduser 2 having a client system 12, a third user 3 having a client system13, and a beacon device 14. The client systems 11, 12, 13 and the beacondevice 14 can be used to access and interact with an event managementapplication 30 hosted on a cloud-based server 31 via network 20. Forexample, the first user 1 is an event organizer using the eventmanagement application 30 to create and manage a specific event, whilethe second user 2 is a customer using the event management system toview upcoming events, and possibly to register for and/or purchasetickets to attend an event. The third user 3 is a customer attending anevent, and the beacon device 14 is located at the event being attendedby the third user 3.

In one embodiment, the cloud-based server 31 is a network-addressablecomputing system hosting a web service that runs the event-managementapplication 30 as a tool for users to organize and manage events. Theevent-management application 30 can include a number of differentfunctional modules which may be an integral part of the event-managementapplication, or which may stand alone as discrete and separate relatedprogram modules that are integrated as part of an event managementsystem or process. For example, the event-management application 30 caninclude or integrate a number of functional modules to provide a varietyof different features, such as: (i) an event listing module 40 thatmaintains a listing of events, information regarding the events, andlinks to related web pages; (ii) a ticket/registration module 50 thatallows customers to purchase tickets and/or register for specificevents; (iii) a check-in module 60 that allows customers that havepurchased tickets or registered for an event to check-in at the event;(iv) a beacon module 70 that interacts with dedicated beacon devicesand/or user devices and/or event organizer devices in order to provideprocess flows for delivery to user devices of registered and/or ticketedcustomers attending the event, or to one or more event organizer devicesoperated by the event organizer, or to one or more beacon devicesconfigured at the event and (v) a point of sale module 80 that allowscustomers to purchase tickets, registrations, merchandise andconcessions at an event. Other functions could also be configured aspart of the event management application.

The event-management application 30 may generate, store, receive, ortransmit event-related data, for example, event listings, eventinformation details, event history details, event registration details,event organizer details, event attendee details, ticket purchasedetails, attendee check-in details, event displays, sponsors, etc. Usersmay access, send data to, and receive data from the event-managementapplication 30 using client systems, such as client systems 11, 12, 13,which may be any suitable computing device, for example, a personalcomputer, a laptop, a tablet, a cellular phone, a smartphone, a personaldigital assistant, etc.

Network 20 may be any suitable communications network. For example, oneor more portions of network 20 may include an ad hoc network, anintranet, an extranet, a virtual private network (VPN), a local areanetwork (LAN), a wireless LAN (WLAN), a wide area network (WAN), awireless WAN (WWAN), a metropolitan area network (MAN), a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), acellular telephone network, another suitable network, or a combinationof any of these.

The client systems 11, 12, 13 and event-management application 30 areconnected to network 20 (or to each other in alternative embodiments) byconnections 15. In some embodiments, the client systems 11, 12, 13 maycommunicate directly with the functional modules of the event managementapplication 30 for a specific purpose. For example, connection 15 aallows direct communication with the event listings module 40, which maybe embodied as a discrete and separate web page; connection 15 b allowsdirect communication with the check in module 60, which may be embodiedas a separate and distinct computing system operated at the event; andconnection 15 c allows direct communication with the beacon module 70.

The connections 15, 15 a, 15 b, 15 c may include one or more wirelineconnections, such as Digital Subscriber Line (DSL) or Data Over CableService Interface Specification (DOCSIS); wireless connections, such asWi-Fi or Worldwide Interoperability for Microwave Access (WiMAX); oroptical connections, such as Synchronous Optical Network (SONET) orSynchronous Digital Hierarchy (SDH). One or more connections 15, 15 a,15 b, 15 c may include an ad hoc network, an intranet, an extranet, aVPN, a LAN, a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, aportion of the PSTN, a cellular telephone network, another suitableconnection, or a combination of any such connections.

In one embodiment, the check-in module 60, the beacon module 70 and thepoint of sale module 80 may be configured as separate and distinctcomputer-based devices located at an event, or they may be integratedwith an event organizer device 32 at the event. Thus, user 3 may be ableto communicate directly with the check-in module 60 via connection 16 a,directly with the beacon module 70 via connection 16 b, and directlywith the point of sale module via connection 16 c, or indirectly withany of these modules via connection 15 d and the network 20. Similarly,the beacon device 14 may be able to communicate directly with thecheck-in module 60 via connection 16 d, directly with the beacon module70 via connection 16 e, directly with the point of sale module viaconnection 16 f, or indirectly with any of these modules via connection15 e and the network 20. The connections 16 a-f may implement a localcommunications protocol, such as Bluetooth LE or Wi-Fi.

3. Event Management Generally

A web-based software application for event-management, such as theEventbrite event management platform, allows a user to create, organizeand manage events. The event may be a party, a concert, a conference, asporting event, a fundraiser, a networking event, or a live performance,for example. Events may occur online (such as a web-based seminar) andoffline (such as a live seminar in a lecture hall). An offline event maytake place at or in a stadium, a hall, an auditorium, a hotel, a campsite, a beach, a standing area, a general admission area, or anysuitable outdoor and indoor locations.

As noted above, the first user 1 of the event management application mayact as an event organizer and, as a starting point, create an eventprofile for one or more events and input information associated with theevent to the event listings module 40 of the event managementapplication. The event profile may be accessed by other users on one ormore web pages or other content sources maintained, for example, in theevent listing module 40 and served through the event-managementapplication 30. The second user 2 of the event management applicationmay be interested in attending an event and use the event-managementsystem, for example, by accessing one or more web pages maintained bythe event listing module 40, to get information about the event, andthen register and/or purchase tickets for the event, for example, bybeing redirected to the ticketing/registration module 50. The third user3 may use the event management system while at the event location forvarious specific event-related tasks, for example, to register orpurchase tickets for the event, or to check in to the event, to purchasefood or merchandise at the event, etc.

The event management system may maintain event profiles for a largenumber of events at a large number of different venues. The eventprofiles may be managed by the event listing module 40 and accessed vianetwork 20 by any suitable client system either directly via connection15 a, or via the event management application 30.

An event profile may include event information related to and describingthe event, included but not limited to, the event title, the eventdate/time, the event category or type, the event details, a descriptionof the event, the event cost or ticket price for the event, the eventorganizer, the event promoter, the geographic location of the event, thevenue for the event, a seat map for the event, the capacity for theevent venue, the performer(s) for the event, the number of ticketsavailable for the event, the type/class of tickets available for theevent, the ticket identifiers, the number of reserved seats availablefor the event, the location/type/class of reserved seats available forthe event, the selling prices of the reserved seats for the event, theselling order of the reserved seats for the event, the registered eventattendees, the check-in status of each event attendee, theticket-selling window (such as a start time and an end time during whichtickets can be sold), purchase information for the event, an attendeelist for the event, references to additional information (such as, forexample, hypertext links to resources related to or describing theevent, historical sales data for the seats of the events, and the like),privacy settings for the event profile, or other suitable eventinformation.

The event profile may also include a total number and type of ticketsthat are available for the event, and a link to purchase tickets or toregister for an event, for example, a link to the ticketing/registrationmodule 50. The type of tickets available for an event may include, forexample, premium tickets, general admission tickets, reserved seattickets, another suitable type or class of tickets, or two or more suchtypes of tickets. The number of tickets available for an event may bebased on a specified number, or the size or capacity of the event venue,or other relevant factors.

The event profile may include reserved seat information for the event.The reserved seat information may include, for example, seatingarrangements for the event at the specified location, the total numberof reserved seats for sale by the event organizer for each seatingarrangement, the location or position of each reserved seat withreference to each seating arrangement, the location or position of eachdoor with reference to each seating arrangement, the location orposition of each wheelchair seat with reference to each seatingarrangement, the type or class of each reserved seats, an estimatedselling price for each reserved seat, a selling order for each reservedseat, or other suitable reserved seats information.

The event management system may include additional software tools toenable a user to promote and manage events. For example, software toolscan provide features such as delivering event information to users viaemail, push notification, text or messaging, including sendingpersonalized invitations to pre-determined contacts, listing non-privateevents on search engine or in public directories, or promoting events tofriends via social networks such as Facebook, Twitter, or Linkedin. Theevent management system may enable the event organizer to trackattendance, including but not limited to, emailing attendees and sendingevent reminders regarding tickets, seating and/or other eventinformation, managing group registration, sending professionalinvitations, viewing ticket sales and/or registration information,determining the number of attendees, estimating the total revenue fromsales of the reserved seats, tracking the sale of each reserved seat,accessing sales data at any time, scanning tickets, and managingdiscounts, group and members-only registration.

4. On-Site Event Management

FIG. 2 illustrates an embodiment of an event management system 100located at an event that includes an event organizer device 130configured with at least a client component of the event managementapplication 30. The event organizer device 130 includes an eventcheck-in system 160 located at the event. The event organizer device 130can be a stand-alone computer-based system, including a personalcomputer, a laptop, a tablet, a cellular phone, a smartphone, a personaldigital assistant, etc., located at the site of the event, but may alsobe connected to the event management server 31. The event check insystem 160 may also be a stand-alone computing device, or it may be anintegrated component of the event organizer device 130. A list ofattendees (registered and/or ticketed) for the event is stored in theevent management system and can be retrieved and used as necessary bythe event organizer device 130 and the check-in system 160 in order toperform event-related routines for the attendees at the event. Otherinformation may also be stored and associated with each attendee, suchas a user profile of the attendee, electronic payment methods, etc.

The attendee list can indicate the status for each attendee registeredfor the event, i.e., has an attendee checked-in at the event or not. Thecheck-in system 160 can be configured in different ways to receive anindication that the attendee has arrived at an event. For example, thecheck-in system 160 can be used to access the event attendee list,either by an event staff person or the attendee himself, and select theattendee from the list to indicate that the attendee has arrived. Thecheck-in system 160 may be configured to allow a search for the eventattendees by name, email address, ticket identifier, etc., and thenselect the attendee from the list.

The check-in system 160 may also be configured to scan a ticket for aticket identifier and to identify the attendee based on the ticketidentifier. The ticket identifier may be a barcode, a 2D barcode, a QRcode, or another suitable scannable identifier. The ticket identifiermay be scanned using any suitable scanning device, such as, for examplea camera, an optical scanner, a barcode scanner, a QR code scanner.

As another example, an attendee may transmit a message or signal, suchas an email, text message, radio frequency identification tag, BluetoothUID, Bluetooth MAC Address, other suitable message or signal, or anycombination thereof, to the check-in system 160, the message or signalcontaining the attendee's name, email address, or ticket identifier. Thecheck-in system 160 receives the message or signal and automaticallyprovides an indication that the attendee has arrived and checked-in.When the attendee exits the event or otherwise leaves the event, theattendee may have his ticket scanned upon exit, or may used the check-insystem 160 to provide an indication that he is leaving the event.

Systems and methods for checking-in attendees to an event are furtherdescribed in U.S. Pat. No. 8,397,984 entitled System for On-siteManagement of an Event, and U.S. Patent Publication No. 2014/0039945entitled Customized Check-In for Event Ticket Network Systems, both ofwhich are completely incorporated herein by reference.

As shown in FIG. 2, the user 102 checks-in to the event using a mobileclient device 112 and a check-in system 160 with the event organizerdevice 130 configured as a wireless access terminal. The mobile clientdevice 112 accesses and/or stores an electronic ticket that istransmitted to the check-in system 160 via a wireless link. The check-insystem 160 verifies whether the electronic ticket is valid and, if so,updates the status of the attendee to indicate that the attendee haschecked-in.

The check-in system 160 with wireless access terminal 130 may beconfigured, for example, using a near-field communication (NFC) system,a radio-frequency identification (RFID) system, another suitable system,or any combination thereof. An NFC interface allows for close-rangecommunication, and may comply with various standards, such as, forexample, ISO/IEC 18092, ECMA-340, ISO/IEC 21481, ECMA-352, ISO 14443,ISO 15693, other suitable standards, or any combination thereof.However, the NFC interface has a very limited range of approximately 2-4cm.

The use of beacon devices at an event can facilitate a more efficientflow of information between the user and the event management system atgreater distances than that of NFC or RFID schemes. The use of beacondevices to periodically and repeatedly transmit information usingwireless communication protocols is generally known. A beacon generatingdevice generates its information in a compact format and transmits theinformation periodically within its range using, for example, theBluetooth Low Energy protocol or the iBeacon protocol. In oneembodiment, a standard advertising beacon is configured to periodicallytransmit a unique identifier (“UID”), e.g., a numeric or alphanumericstring that is uniquely associated with the advertising beacon. The UIDis typically used to address or reference the beacon device, and may bea MAC address, a Bluetooth UUID, or any other identifier schemeincluding a custom address. The transmission of the beacon UID isreceived by any mobile communication devices (e.g., smartphone) locatedwithin range of the beacon, typically about 50 meters.

In one embodiment, one or more beacon devices can be deployed at anevent and configured to transmit information or to receive informationthat is used to initiate and perform specific event-related processflows. The use of beacons makes the event-related processes moreefficient and user friendly. In one example, referring to FIG. 2, thecheck-in system 160 at the event may be configured to generate andtransmit a beacon. The mobile client device 112 detects the transmissionof information from the beacon and sends the information received, suchas a UID, to the event management application 30 on the server 31 vianetwork 20. The event management system 30 then searches for thereceived information on the event management application or in datastorage accessible to the server. If it finds a match, the eventmanagement system initiates a specific process flow or action associatedwith the matched information, which usually results in information, suchas data, content, or code for a specific event-related process flow,being provided from the event management server 31 back to the mobileclient device 112, or to the event organizer device 130. The user 102then performs the specific process flow or action using the mobileclient device 112, for example, by swiping the client device to check into the event, which then interacts with the check in device 160 and/orthe event organizer device 130 via the event management application 30on the server 31 via network 20 using a Bluetooth wireless link, ordirectly with check in device 160 and/or the event organizer device 130.

The completion of the process flow on the mobile client device 112causes data and/or instructions to be sent to event management system 30via the network 20. The event management system 30 then sends furtherinstructions back to the check in device 160, or the event organizerdevice 130, to complete the event process flow, for example,acknowledging the user check-in, and updating the attendee list on theserver.

Typically, the mobile client device 112 has at least a client componentof the event management application installed. The operating system ofthe mobile client device 112 can be configured to listen for a list ofspecific signals, such as one or more UIDs related to an event that theuser has registered or purchased tickets for using the event managementsystem. Alternatively, the operating system of the mobile client device112 can be configured to listen for any and all signals that arebroadcast within range of the device, and then look for those signals onthe event management system using specified search criteria, such asgeolocation data, registration purchase history, etc. When a listed UIDor other signal is detected, an action may be specified, as furtherdiscussed below.

For example, when a client component of the event management applicationis installed on the mobile client device 112, the user may registervarious UIDs that should be listened for. The ability to specify andlisten for specific transmissions is a standard feature of mostoperating systems, including the Apple iOS. Further, such aconfiguration is usually run in the background, and the application neednot be open or running. When a listed UID is detected, an action may bespecified, for example, wake up the device, start the event managementapplication, and send the detected UID to the event management server31.

One example of the use of beacons is illustrated in FIG. 3. An eventlocation 200 is shown that includes a stage 201, a seating area 202, anda concessions area 203, all located within a perimeter fence 204. Anentrance area 205 is located outside the perimeter fence 204 but withinits own perimeter fence 206. The entrance area 205 is configured tofunnel guests arriving at the main gate 210 to one of three entrances:gate A with check-in system 261; gate B with check-in system 262; andgate C with check-in system 263.

A number of beacon generating transmitters are distributed around theevent location 200. For example, a first beacon 280 is located at theinlet to the entrance area 205. The first beacon is configured totransmit a first UID that will be received by any mobile client systemthat is within range of the first beacon, i.e., any device that isentering the entrance area 205. A user device that includes at least aclient component of the event management application and that haspurchased a ticket to the event using the event management applicationwill recognize the first UID and send the first UID to the eventmanagement server. The server will return information to the userdevice, such as program instructions and/or data for a firstevent-related process flow specifically associated with the first UID.In this example, the flow associated with the first UID may beinstructions for guests as to which gate they should use to enter theseating area. Such an instruction could be customized for the particularuse based on, for example, a ticket identifier that is associated withthat user for that event. Thus, guests with seats nearer the stage atthe front of the seating area may be directed to gate A; guests withseats in the rear of the seating area may be directed to gate B; guestswith seats in the balcony may be directed to gate C.

An alternative process flow 300, illustrated in FIG. 4, may provide theopportunity to purchase a ticket for the event. For example, if the useris at the event but without a ticket, in step 302, the user devicedetects the transmission of the first UID from beacon 280. In step 304,the user device sends the first UID to the event management server. Instep 306, the server retrieves a process flow associated with the firstUID from storage, such as program instructions regarding the purchase oftickets. In step 308, the server returns the purchase instructions tothe user device. For example, the server may provide a link to a webpage dedicated to purchase transactions for the event. In step 310, theuser device performs the process flow for the purchase transaction,which may include interaction with the server 31 or a third partypayment service. In one embodiment, performing the process flow causesthe user device to be redirected to the web page for purchasetransactions, where the user can initiate and complete the purchasetransaction.

Once the purchase transaction is complete in step 312, the user devicenotifies the server in step 314. In step 316, the server updates thestatus of the user for that event.

If the user device has already installed the client component of eventmanagement application, the user can also configure payment credentialsthat are associated with the user account in the event managementapplication. For example, the event management application may have a“wallet” tool that is associated with the user account and configuredwith payment credentials for any purchase transaction initiated by theuser. Alternatively, the event management application may be linked bythe user to a third party payment authorization method, such as ApplePay or Google Wallet.

Further, for such purchase transactions, an additional security layermay be provided as part of the purchase transaction process flow. Forexample, the process flow for a purchase transaction may require theuser to enter a security code to complete the transaction, such as thelast four digits of the payment credit card associated with the account,a confirmation code emailed or messaged to the user, or other similarsecurity feature.

Referring back to FIG. 3, a second beacon 281 is located at gate A, anda third beacon 282 is located at gates B and C. The second beacon 281 isconfigured to transmit a second UID, and the third beacon 282 isconfigured to transmit a third UID. At the entry gates A, B and C, aprocess flow for admitting and checking in users with a validregistration or ticket can be performed. For example, as illustrated inFIG. 5, in step 402, the user device detects the transmission of eitherthe second or third UID from beacon 281 or beacon 282, respectively. Instep 404, the user device sends the detected UID to the event managementserver. In step 406, the server retrieves a process flow associated withthe detected UID from storage, such as program instructions regardingcheck-in to the event. In step 408, the server returns the check-ininstructions to the user device. For example, the server may provideinstructions to issue a notification to the user device, such as “Youhave arrived at the Event. Swipe to check in.” In step 410, the userdevice performs the instructions for the check-in process flow, forexample, by displaying the notification on the user device. In step 412,the user interacts with or responds to the notification displayed on theuser device in order to proceed with the check-in process. In step 414,in response to the user interaction, the user device sends instructionsback to the server to proceed with the check-in process. In step 416,the server confirms that the user has a valid ticket for the event. Instep 418, the server updates the user status for the event to indicatethat the user has been admitted or checked-in to the event. In step 420,the server returns instructions to the check-in device 160, for example,confirming that the user has a valid ticket and should be admitted, andin step 421, the check-in device displays a message, e.g., confirming asuccessful check-in. In step 422, the server returns instructions to theuser device, for example, to display a message in step 423 confirming asuccessful check-in.

A fourth beacon 283 is located in the concessions area. The fourthbeacon 283 is configured to transmit a fourth UID, which is sent by theuser device to the server to initiate a fourth flow associated with thefourth UID. For example, customized content can be sent to user devices,such as coupons for drinks or merchandise in the concessions area.

A fifth beacon 284 is located at a designated VIP area 207 near thestage 201. For example, the VIP area 207 may be backstage or a dedicatedroom or tent next to the stage requiring special access privileges. Thefifth beacon 284 is configured to transmit a fifth UID, which isdetected and sent by the user device to the server to initiate a fifthflow associated with the fifth UID. For example, FIG. 6 illustrates aprocess flow 500 for granting access to the VIP area 207. In step 502,the user device detects the transmission of the fifth UID from beacon284. In step 504, the user device sends the detected UID to the server.In step 506, the server retrieves a process flow associated with thedetected UID from storage, such as program instructions regarding accessto the VIP area 207. In step 508, the server returns the VIP accessinstructions to the user device. For example, the server may provideinstructions to generate a notification to the user device regarding thestatus of the user vis a vis access to the VIP area 207. The accessprivilege may be indicated by a particular class of ticket, e.g., apremium ticket having an extra charge for the access privilege, or anyother suitable scheme to provide restricted access. For example, in step510, the instructions sent to the user device may include the user'sticket status and cause a notification to be displayed on the userdevice such as “You may enter the VIP area. Slide to displayauthorization,” or alternatively, “You do not have access to the VIParea.” In step 512, the user interacts with or responds to the displayednotification, for example, by sliding the notification to reveal the VIPaccess authorization, or additional options. In step 514, the userdevice sends instructions back to the server confirming that the userhas revealed and used the VIP authorization to enter the VIP area 207.In step 516, the server updates the user status for the event toindicate that the user has been admitted to the VIP area 207.

In one embodiment, the beacon device can be integrated with a componentof the event management system, for example, the check-in systems, pointof sale systems, informational systems, etc., but the beacon devicecould also be a stand-alone device.

In general, any computer-based device can be configured to transmit abeacon signal and/or listen for a beacon signal. Thus, in an alternativeembodiment, the user's mobile communications device may be operated as abeacon generating device while a beacon device, or more generally, aclient computing device such as the event organizer device, may beconfigured to listen for and process the generated beacon signal asdescribed above to initiate a programmed response.

For example, a process 600 for using the user device as a beacongenerating device is illustrated in FIG. 7A. In step 602, a user logsinto the event management application on the cloud-based server with theuser's credential, such as login ID and password. In step 604, while theuser device is logged into the event management application, the UID ofthe user device is registered with the event management application onthe server. Typically, the registration of the user device UID with theevent management application on the server takes place automatically inaccord with the configuration of the event management application. Thus,the user is ordinarily not required to manually register his device withthe server. The registration may take place well before an event, forexample, when the user purchases a ticket to the event with the eventmanagement application or when the user responds to a question on theevent management application soliciting the UID.

In step 606, the event management application associates any events forwhich the user has registered or purchased tickets with the user deviceUID on the event management server, and the registration or purchasedticket is also associated with the UID of the user device. Thus, theevent management application can maintain a listing for each event ofall UIDs associated with users that have purchased tickets and/orregistered for that event. In step 608, the server can download thelisting of all UIDs having tickets and/or registrations for a specificevent to the event organizer device that is present at the eventlocation so that the event organizer device knows which UIDs to listenfor at the event. In step 610, the event organizer device detects thetransmission of one or more UIDs at the event location. In step 612, theevent organizer device sends the one or more detected UIDs to theserver, or looks up the UIDs in the downloaded list. In step 614, theserver or event organizer device retrieves a process flow associatedwith each specific UID and sends the respective process flows eitherback to the event organizer device, or alternatively, directly to theuser device. In step 616, the process flow is performed. Usually, theprocess flow involves one or more interactions of data and instructionscommunicated between the user device and/or the event device and/or theserver.

Another process 650 for using the user device as a beacon generatingdevice is illustrated in FIG. 7B. Steps 602, 604 and 606 are the same asin FIG. 7. In step 652, the server downloads not only the listing of allUIDs having tickets and/or registrations for a specific event to anevent organizer device at the event location, but also the process flowsthat are associated with each UID, and the UIDs and process flows arestored (at least temporarily) on the event organizer device orassociated storage. In step 654, the event organizer device detects thetransmission of a UID at the event location. In step 656, the eventorganizer device retrieves the process flows associated with thedetected UID from storage, and in step 658, the process flow isperformed.

In general, the process flow may be any event-related task. For example,the process flow may enable a check-in procedure for the user, or mayenable the user to purchase a ticket and/or register for the event, ormay enable the user to purchase merchandise and/or concessions at theevent, or may initiate a customer service interaction, among othertasks.

In one embodiment, a beacon could be placed within a kiosk that wouldotherwise be used to conduct ticket sales at the event. The beacon couldbe limited to a certain broadcast range, such as within a circlecentered on the kiosk. A sign could indicate an action required byprospective purchasers, such as “Step In To Purchase.” The prospectivepurchaser would then trigger the transmission or reception of aparticular purchase beacon by following such directions. The purchaserwould then receive an event related process flow related to purchasingtickets (or other goods or services) via the process described in moredetail above. The effect would be to greatly reduce lines and congestionat key locations within an event.

In one embodiment, a user with a valid ticket can simply walk through agate at the event, and the event device, having already detected thebeacon transmission with the UID of the user's device, automaticallyvalidates the ticket and checks the user into the event without anyfurther action on the user's part.

In another example, when the event device detects the UID of the userdevice, the event device initiates a process flow for a check-inprocedure that may be downloaded directly to the user device from theserver or from the event device. The process flow may automaticallydisplay the user's ticket, or more typically, to avoid interruptingsomething that the user is doing with his device, such as a telephonecall or browsing the internet, a notification is presented to the userdevice. For example, the notification may be a pop-up message displayedon the home screen of the user device that says “slide to displayticket” or “slide to view check-in options” or other similar messages.

Numerous different event-related flows and actions can be initiated as aresult of strategically placing one or more beacon devices at an eventlocation to either transmit a UID or listen for other device UIDs. Forexample, the beacons may be associated with specific process flows thatcan be delivered to the user's device and/or the event organizer deviceand that are directed to the following features: (i) allowing the userto purchase tickets electronically using a mobile communications device;(ii) checking the user in at the event; (iii) validating the user'sticket; (iv) providing directions to seating, concessions, and otherfacilities at the event; (v) providing information and/or coupons forconcessions and other merchandise at the event; (vi) providing theability for a user to purchase concessions and other merchandise at theevent using electronic payment methods with a mobile communicationsdevice; (vii) providing the ability to upgrade access level or assignedseats. Many other event-related features can be provided throughappropriate instructions and process flows.

5. Exemplary Hardware Architecture

FIG. 8 illustrates one example of a computer system 1000 for performingone or more steps of one or more methods described or illustratedherein. Reference herein to a computer system may include any type ofcomputing device, or may include one or more computer systems, whereappropriate.

The computer system 1000 may take any suitable physical form. As oneexample, computer system 1000 may be an embedded computer system, asystem-on-chip (SOC), a single-board computer system (SBC) (such as, forexample, a computer-on-module (COM) or system-on-module (SOM)), adesktop computer system, a laptop or notebook computer system, aninteractive kiosk, a mainframe, a mesh of computer systems, a mobiletelephone, a personal digital assistant (PDA), a server, a tabletcomputer system, or a combination of two or more of these. Whereappropriate, computer system 1000 may include one or more computersystems; be unitary or distributed; span multiple locations; spanmultiple machines; span multiple data centers; or reside in a cloud,which may include one or more cloud components in one or more networks.Further, one or more computer systems 1000 may perform the steps ormethods at different times or at different locations, where appropriate.

In one embodiment, the computer system 1000 includes a processor 1002,memory 1004, storage 1006, an input/output (I/O) interface 1008, acommunication interface 1010, and a bus 1012. However, this disclosurecontemplates any suitable computer system having any number of anyrelevant components in an effective arrangement.

Processor 1002 may include hardware for executing instructions, such asthose making up a computer program. In order to execute instructions,the processor 1002 may retrieve (or fetch) the instructions from aninternal register, an internal cache, memory 1004, or storage 1006;decode and execute them; and then write one or more results to aninternal register, an internal cache, memory 1004, or storage 1006.Processor 1002 may include one or more internal caches for data,instructions, or addresses. The processor 1002 may include one or moreinstruction caches, one or more data caches, and one or more translationlookaside buffers (TLBs). Instructions in the instruction caches may becopies of instructions in memory 1004 or storage 1006, and theinstruction caches may speed up retrieval of those instructions byprocessor 1002. Data in the data caches may be copies of data in memory1004 or storage 1006 for instructions executing at processor 1002 tooperate on; the results of previous instructions executed at processor1002 for access by subsequent instructions executing at processor 1002or for writing to memory 1004 or storage 1006; or other suitable data.The data caches may speed up read or write operations by processor 1002.The TLBs may speed up virtual-address translation for processor 1002.

The processor 1002 may include one or more internal registers for data,instructions, or addresses. Where appropriate, processor 1002 mayinclude one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors.

Memory 1004 includes main memory for storing instructions for processor1002 to execute or data for the processor to operate on. Computer system1000 may load instructions from storage 1006 or another source (such as,for example, another computer system) to memory 1004. Processor 1002 maythen load the instructions from memory 1004 to an internal register orinternal cache. To execute the instructions, processor 1002 may retrievethe instructions from the internal register or internal cache and decodethem. During or after execution of the instructions, processor 1002 maywrite one or more results (which may be intermediate or final results)to the internal register or internal cache. Processor 1002 may thenwrite one or more of those results to memory 1004.

Processor 1002 executes only instructions or data in one or moreinternal registers or internal caches or in memory 1004 (as opposed tostorage 1006 or elsewhere). One or more memory buses (which may eachinclude an address bus and a data bus) may couple processor 1002 tomemory 1004. Bus 1012 may include one or more memory buses, as describedbelow.

One or more memory management units (MMUs) may reside between processor1002 and memory 1004 and facilitate access to memory 1004 requested bythe processor. Memory 1004 may include random access memory (RAM), whichmay be volatile memory, dynamic RAM (DRAM) or static RAM (SRAM).Moreover, where appropriate, this RAM may be single-ported ormulti-ported RAM.

Storage 1006 may include mass storage for data or instructions. Storage1006 may include a hard disk drive (HDD), a floppy disk drive, flashmemory, an optical disc, a magneto-optical disc, magnetic tape, or aUniversal Serial Bus (USB) drive or a combination of two or more ofthese. Storage 1006 may include removable or non-removable (or fixed)media, where appropriate. Storage 1006 may be internal or external tocomputer system 1000, where appropriate. Storage 1006 may benon-volatile, solid-state memory, read-only memory (ROM),mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM),electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM),or flash memory or a combination of two or more of these. Storage 1006may include one or more storage control units facilitating communicationbetween processor 1002 and the storage, where appropriate.

I/O interface 1008 includes hardware, software, or both, providing oneor more interfaces for communication between computer system 1000 andone or more I/O devices. Computer system 1000 may include one or more ofthese I/O devices, where appropriate, to enable communication between auser and the computer system. An I/O device may include a keyboard,keypad, microphone, monitor, mouse, printer, scanner, speaker, stillcamera, stylus, tablet, touch screen, trackball, video camera, anothersuitable I/O device or a combination of two or more of these. An I/Odevice may include one or more sensors. I/O interface 1008 may includeone or more device or software drivers enabling processor 1002 to driveone or more of these I/O devices.

Communication interface 1010 may include hardware, software, or bothproviding one or more interfaces for communication (such as, forexample, packet-based communication) between computer system 1000 andone or more other computer systems or one or more networks.Communication interface 1010 may include a network interface controller(NIC) or network adapter for communicating with an Ethernet or otherwire-based network or a wireless NIC (WNIC) or wireless adapter forcommunicating with a wireless network, such as a WI-FI network. Computersystem 1000 may communicate with an ad hoc network, a personal areanetwork (PAN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), or one or more portions of the Internetor a combination of two or more of these. One or more portions of one ormore of these networks may be wired or wireless. Computer system 1000may communicate with a wireless PAN (WPAN) (such as, for example, aBLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephonenetwork (such as, for example, a Global System for Mobile Communications(GSM) network), or other suitable wireless network or a combination oftwo or more of these.

Bus 1012 may include hardware, software, or both coupling components ofcomputer system 1000 to each other. Bus 1012 may include an AcceleratedGraphics Port (AGP) or other graphics bus, an Enhanced Industry StandardArchitecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT)interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBANDinterconnect, a low-pin-count (LPC) bus, a memory bus, a Micro ChannelArchitecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, aPCI-Express (PCIe) bus, a serial advanced technology attachment (SATA)bus, a Video Electronics Standards Association local (VLB) bus, oranother suitable bus or a combination of two or more of these.

A non-transitory computer-readable storage medium may include one ormore semiconductor-based or other integrated circuits (ICs) (such, asfor example, field-programmable gate arrays (FPGAs) orapplication-specific Ics (ASICs)), hard disk drives (HDDs), hybrid harddrives (HHDs), optical discs, optical disc drives (ODDs),magneto-optical discs, magneto-optical drives, floppy diskettes, floppydisk drives (FDDs), magnetic tapes, solid-state drives (SSDs),RAM-drives, SECURE DIGITAL cards or drives, any other suitablenon-transitory computer-readable storage media, or any suitablecombination of two or more of these, where appropriate. Acomputer-readable non-transitory storage medium may be volatile,non-volatile, or a combination of volatile and non-volatile, whereappropriate.

The scope of this disclosure encompasses all changes, substitutions,variations, alterations, and modifications to the example embodimentsdescribed or illustrated herein that a person having ordinary skill inthe art would comprehend. The scope of this disclosure is not limited tothe example embodiments described or illustrated herein. Moreover,although this disclosure describes and illustrates herein components,elements, feature, functions, operations, or steps, any of theseembodiments may include any combination or permutation of any of thecomponents, elements, features, functions, operations, or stepsdescribed or illustrated anywhere herein that a person having ordinaryskill in the art would comprehend. Furthermore, reference in theappended claims to an apparatus or system or a component of an apparatusor system being adapted to, arranged to, capable of, configured to,enabled to, operable to, or operative to perform a particular functionencompasses that apparatus, system, component, whether or not it or thatparticular function is activated, turned on, or unlocked, as long asthat apparatus, system, or component is so adapted, arranged, capable,configured, enabled, operable, or operative.

1. A method comprising: detecting, by a first event computing devicelocated at a first area of an event venue, at least a first uniqueidentifier being periodically transmitted by a first user computingdevice; retrieving, by the first event computing device, a first set ofinstructions associated with the first unique identifier, the first setof instructions configured for authorizing access to the first area ofthe event venue; receiving, by the first event computing device from thefirst user computing device after execution of the first set ofinstructions by one of the first user computing device or the firstevent computing device, a first ticket identifier; determining, by thefirst event computing device, that the first ticket identifier is avalid ticket identifier for the first area; upon determining that thefirst ticket identifier is a valid ticket identifier for the first area,enabling access to the first area for a holder of the first usercomputing device; detecting, by a second event computing device locatedat a second area of the event venue located within the first area, thefirst unique identifier being periodically transmitted by the first usercomputing device; retrieving, by the second event computing device, asecond set of instructions associated with the first unique identifier,the second set of instructions configured for authorizing access to thesecond area of the event venue; determining, by the second eventcomputing device, that the first ticket identifier is a valid ticketidentifier for the second area; upon determining that the second ticketidentifier is a valid ticket identifier for the second area, enablingaccess to the second area for the holder of the first user computingdevice.
 2. The method of claim 1, further comprising: downloading, bythe first event computing device from an event management server, a listhaving a plurality of unique identifiers including the first uniqueidentifier, a plurality of unique users each respectively associatedwith one of the plurality of unique identifiers including a first userassociated with the first unique identifier, a plurality of valid ticketidentifiers each respectively associated with one of the plurality ofunique users including the first ticket identifier associated with thefirst user, and each of the plurality of valid ticket identifiersconfigured to enable access to at least the first area.
 3. The method ofclaim 2, the step of determining that the first ticket identifier is avalid ticket identifier for the first area further comprising comparingthe first ticket identifier to the plurality of valid ticket identifierson the list of unique identifiers.
 4. The method of claim 2, furthercomprising configuring the first event computing device to listen forthe plurality of unique identifiers.
 5. The method of claim 1, furthercomprising: downloading, by the second event computing device from anevent management server, a list having a plurality of unique identifiersincluding the first unique identifier, a plurality of unique users eachrespectively associated with one of the plurality of unique identifiers,a plurality of valid ticket identifiers each respectively associatedwith one of the plurality of unique users, and at least one of theplurality of valid ticket identifiers configured to enable access to thesecond area.
 6. The method of claim 5, the step of determining that thefirst ticket identifier is a valid ticket identifier for the second areafurther comprising comparing the first ticket identifier to theplurality of valid ticket identifiers on the list of unique identifiers.7. The method of claim 5, further comprising configuring the secondevent computing device to listen for the at least one of the pluralityof unique identifiers.
 8. The method of claim 1, the step of determiningthat the first ticket identifier is a valid ticket identifier for thefirst area further comprising: transmitting, by the first eventcomputing device to an event management server, the detected uniqueidentifier; and receiving, by the first event computing device, thefirst set of instructions from the event management server.
 9. Themethod of claim 1, the step of determining that the first ticketidentifier is a valid ticket identifier for the second area furthercomprising: transmitting, by the second event computing device to theevent management server, the detected unique identifier; and receiving,by the second event computing device, the second set of instructionsfrom the event management server.
 10. The method of claim 1, the firstunique identifier is the first ticket identifier.
 11. The method ofclaim 1, the step of enabling access to the first area furthercomprising providing a notification to the first user computing devicethat access to the first area has been enabled.
 12. The method of claim11, further comprising: providing a third set of instructions to thefirst user computing device; and receiving an appropriate response fromthe first user computing device.
 13. The method of claim 12, furthercomprising: requesting a scan of the first ticket identifier; receivingthe scan of the first ticket identifier.
 14. A method comprising:detecting, by a first event computing device located at a first area ofan event venue, a plurality of unique identifiers each beingperiodically transmitted by a respective one of a plurality of usercomputing devices; comparing, by the first event computing device, eachof the detected unique identifiers to a list having a plurality of validunique identifiers that permit access to the first area and a subset ofthe valid unique identifiers that also permit access to a second area ofthe event venue; determining, from the comparison performed by the firstevent computing device, whether each of the detected unique identifiersare valid unique identifiers permitting access to the first area;enabling access to the first area to a user holding one of the pluralityof user computing devices transmitting one of the unique identifiersdetermined to be a valid unique identifier; detecting, by a second eventcomputing device located at the second area, at least one of the uniqueidentifiers determined to be in the subset of valid unique identifiers;comparing, by the second event computing device, each of the detectedunique identifiers to the list of valid unique identifiers; determining,from the comparison performed by the second event computing device, thatat least one of the detected unique identifiers is in the subset ofvalid unique identifiers permitting access to the second area; enablingaccess to the second area to a user holding the respective usercomputing device transmitting the at least one detected uniqueidentifier determined to be in the subset of valid unique identifiers.15. The method of claim 14, further comprising: downloading, by thefirst event computing device and second event computing device from anevent management server, the list.
 16. The method of claim 14, the stepof enabling access to the first area further comprising providing anotification to the first user computing device that access to the firstarea has been enabled.
 17. The method of claim 16, further comprising:providing a third set of instructions to the first user computingdevice; and receiving an appropriate response from the first usercomputing device.
 18. An event management system, comprising: a firstevent computing device located at a first area of an event venue, thefirst event computing device having a first processor configured with afirst instruction set that, when executed, causes the first processorto: detect a plurality of unique identifiers each being periodicallytransmitted by a respective one of a plurality of user computingdevices; determine, for each of the detected plurality of uniqueidentifiers, that a first subset of the detected plurality of uniqueidentifiers are valid unique identifiers permitting access to the firstarea; enable access to the first area to a user holding one of theplurality of user computing devices transmitting one of the first subsetof the detected unique identifiers determined to be a valid uniqueidentifier; a second event computing device located at a second area ofthe event venue, the second event computing device having a secondprocessor configured with a second instruction set that, when executed,causes the second processor to: detect at least one of the first subsetof the detected plurality of unique identifiers being periodicallytransmitted; determine that the at least one of the first subset of thedetected plurality of unique identifiers is a valid unique identifierpermitting access to the second area; and enable access to the secondarea to a user holding a user computing device the at least one of thefirst subset of the detected plurality of unique identifiers determinedto be a valid unique identifier permitting access to the second area.